﻿<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en"><!--
 Archive processed by SingleFile 
 url: https://tools.ietf.org/html/rfc7037 
 saved date: Sat Oct 18 2014 04:13:23 GMT+0300 (Финляндия (лето)) 
--><head profile="http://dublincore.org/documents/2008/08/04/dc-html/">
    <meta http-equiv="Content-Type" content="text/html; charset=utf-8">
    <meta name="robots" content="index,follow">
    <meta name="creator" content="rfcmarkup version 1.108">
    <link rel="schema.DC" href="http://purl.org/dc/elements/1.1/">
<meta name="DC.Identifier" content="urn:ietf:rfc:7037">
<meta name="DC.Description.Abstract" content="The DHCPv6 RADIUS option provides a mechanism to exchange\nauthorization and identification information between the DHCPv6 relay\nagent and DHCPv6 server. This architecture assumes that the Network\nAccess Server (NAS) acts as both a DHCPv6 relay agent and RADIUS\nclient. When receiving messages from the DHCPv6 clients, the NAS\nconsults the RADIUS server and adds the RADIUS response when\nforwarding the DHCPv6 client\x27s messages to the DHCPv6 server. The\nDHCPv6 server then uses that additional information to generate an\nappropriate response to the DHCPv6 client\x27s requests.">
<meta name="DC.Creator" content="Yeh, L.">
<meta name="DC.Creator" content="Boucadair, M.">
<meta name="DC.Date.Issued" content="October, 2013">
<meta name="DC.Title" content="RADIUS Option for the DHCPv6 Relay Agent">

    <link rel="icon" href="" type="image/png">
    <link rel="shortcut icon" href="" type="image/png">
    <title>RFC 7037 - RADIUS Option for the DHCPv6 Relay Agent</title>
    
    
    <style type="text/css">
	body {
	    margin: 0px 8px;
            font-size: 1em;
	}
        h1, h2, h3, h4, h5, h6, .h1, .h2, .h3, .h4, .h5, .h6 {
	    font-weight: bold;
            line-height: 0pt;
            display: inline;
            white-space: pre;
            font-family: monospace;
            font-size: 1em;
	    font-weight: bold;
        }
        pre {
            font-size: 1em;
            margin-top: 0px;
            margin-bottom: 0px;
        }
	.pre {
	    white-space: pre;
	    font-family: monospace;
	}
	.header{
	    font-weight: bold;
	}
        .newpage {
            page-break-before: always;
        }
        .invisible {
            text-decoration: none;
            color: white;
        }
        a.selflink {
          color: black;
          text-decoration: none;
        }
        @media print {
            body {
                font-family: monospace;
                font-size: 10.5pt;
            }
            h1, h2, h3, h4, h5, h6 {
                font-size: 1em;
            }
        
            a:link, a:visited {
                color: inherit;
                text-decoration: none;
            }
            .noprint {
                display: none;
            }
        }
	@media screen {
	    .grey, .grey a:link, .grey a:visited {
		color: #777;
	    }
            .docinfo {
                background-color: #EEE;
            }
            .top {
                border-top: 7px solid #EEE;
            }
            .bgwhite  { background-color: white; }
            .bgred    { background-color: #F44; }
            .bggrey   { background-color: #666; }
            .bgbrown  { background-color: #840; }            
            .bgorange { background-color: #FA0; }
            .bgyellow { background-color: #EE0; }
            .bgmagenta{ background-color: #F4F; }
            .bgblue   { background-color: #66F; }
            .bgcyan   { background-color: #4DD; }
            .bggreen  { background-color: #4F4; }

            .legend   { font-size: 90%; }
            .cplate   { font-size: 70%; border: solid grey 1px; }
	}
    </style>
    <!--[if IE]>
    <style>
    body {
       font-size: 13px;
       margin: 10px 10px;
    }
    </style>
    <![endif]-->

    
</head>
<body>
   <div style="height: 13px;">
      <div onmouseover="this.style.cursor='pointer';" onclick="showElem('legend');" onmouseout="hideElem('legend')" style="height: 6px; position: absolute;" class="pre noprint docinfo bgblue" title="Click for colour legend.">                                                                        </div>
      <div id="legend" class="docinfo noprint pre legend" style="position:absolute; top: 4px; left: 4ex; visibility:hidden; background-color: white; padding: 4px 9px 5px 7px; border: solid #345 1px; " onmouseover="showElem('legend');" onmouseout="hideElem('legend');">
      </div>
   </div>
<span class="pre noprint docinfo top">[<a href="https://tools.ietf.org/html" title="Document search and retrieval page">Docs</a>] [<a href="https://tools.ietf.org/rfc/rfc7037.txt" title="Plaintext version of this document">txt</a>|<a href="https://tools.ietf.org/pdf/rfc7037" title="PDF version of this document">pdf</a>] [<a href="https://tools.ietf.org/html/draft-ietf-dhc-dhcpv6-radius-opt" title="draft-ietf-dhc-dhcpv6-radius-opt">draft-ietf-dhc-dh...</a>] [<a href="https://tools.ietf.org/rfcdiff?difftype=--hwdiff&amp;url2=rfc7037" title="Inline diff (wdiff)">Diff1</a>] [<a href="https://tools.ietf.org/rfcdiff?url2=rfc7037" title="Side-by-side diff">Diff2</a>] [<a href="https://datatracker.ietf.org/ipr/search/?option=rfc_search&amp;rfc_search=7037" title="IPR disclosures related to this document">IPR</a>]           </span><br>
<span class="pre noprint docinfo">                                                                        </span><br>
<span class="pre noprint docinfo">                                                       PROPOSED STANDARD</span><br>
<span class="pre noprint docinfo">                                                                        </span><br>
<pre>Internet Engineering Task Force (IETF)                            L. Yeh
Request for Comments: 7037                       Freelancer Technologies
Category: Standards Track                                   M. Boucadair
ISSN: 2070-1721                                           France Telecom
                                                            October 2013


                <span class="h1"><h1>RADIUS Option for the DHCPv6 Relay Agent</h1></span>

Abstract

   The DHCPv6 RADIUS option provides a mechanism to exchange
   authorization and identification information between the DHCPv6 relay
   agent and DHCPv6 server.  This architecture assumes that the Network
   Access Server (NAS) acts as both a DHCPv6 relay agent and RADIUS
   client.  When receiving messages from the DHCPv6 clients, the NAS
   consults the RADIUS server and adds the RADIUS response when
   forwarding the DHCPv6 client's messages to the DHCPv6 server.  The
   DHCPv6 server then uses that additional information to generate an
   appropriate response to the DHCPv6 client's requests.

Status of This Memo

   This is an Internet Standards Track document.

   This document is a product of the Internet Engineering Task Force
   (IETF).  It represents the consensus of the IETF community.  It has
   received public review and has been approved for publication by the
   Internet Engineering Steering Group (IESG).  Further information on
   Internet Standards is available in <a href="https://tools.ietf.org/html/rfc5741#section-2">Section&nbsp;2 of RFC 5741</a>.

   Information about the current status of this document, any errata,
   and how to provide feedback on it may be obtained at
   <a href="http://www.rfc-editor.org/info/rfc7037">http://www.rfc-editor.org/info/rfc7037</a>.

















<span class="grey">Yeh &amp; Boucadair              Standards Track                    [Page 1]</span>
</pre><!--NewPage--><pre class="newpage"><a name="page-2" id="page-2" href="#page-2" class="invisible"> </a>
<span class="grey"><a href="https://tools.ietf.org/html/rfc7037">RFC 7037</a>                  DHCPv6 RADIUS Option              October 2013</span>


Copyright Notice

   Copyright (c) 2013 IETF Trust and the persons identified as the
   document authors.  All rights reserved.

   This document is subject to <a href="https://tools.ietf.org/html/bcp78">BCP 78</a> and the IETF Trust's Legal
   Provisions Relating to IETF Documents
   (<a href="http://trustee.ietf.org/license-info">http://trustee.ietf.org/license-info</a>) in effect on the date of
   publication of this document.  Please review these documents
   carefully, as they describe your rights and restrictions with respect
   to this document.  Code Components extracted from this document must
   include Simplified BSD License text as described in <a href="#section-4">Section 4</a>.e of
   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Table of Contents

   <a href="#section-1">1</a>.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   <a href="#page-2">2</a>
   <a href="#section-2">2</a>.  Terminology and Language  . . . . . . . . . . . . . . . . . .   <a href="#page-3">3</a>
   <a href="#section-3">3</a>.  Network Scenarios . . . . . . . . . . . . . . . . . . . . . .   <a href="#page-3">3</a>
   <a href="#section-4">4</a>.  DHCPv6 RADIUS Option  . . . . . . . . . . . . . . . . . . . .   <a href="#page-6">6</a>
     <a href="#section-4.1">4.1</a>.  RADIUS Attributes Permitted in DHCPv6 RADIUS Option . . .   <a href="#page-7">7</a>
   <a href="#section-5">5</a>.  DHCPv6 Relay Agent Behavior . . . . . . . . . . . . . . . . .   <a href="#page-7">7</a>
   <a href="#section-6">6</a>.  DHCPv6 Server Behavior  . . . . . . . . . . . . . . . . . . .   <a href="#page-7">7</a>
   <a href="#section-7">7</a>.  DHCPv6 Client Behavior  . . . . . . . . . . . . . . . . . . .   <a href="#page-7">7</a>
   <a href="#section-8">8</a>.  Security Considerations . . . . . . . . . . . . . . . . . . .   <a href="#page-8">8</a>
   <a href="#section-9">9</a>.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   <a href="#page-8">8</a>
   <a href="#section-10">10</a>. Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .   <a href="#page-9">9</a>
   <a href="#section-11">11</a>. References  . . . . . . . . . . . . . . . . . . . . . . . . .   <a href="#page-9">9</a>
     <a href="#section-11.1">11.1</a>.  Normative References . . . . . . . . . . . . . . . . . .   <a href="#page-9">9</a>
     <a href="#section-11.2">11.2</a>.  Informative References . . . . . . . . . . . . . . . . .  <a href="#page-10">10</a>

<span class="h2"><h2><a class="selflink" name="section-1" href="#section-1">1</a>.  Introduction</h2></span>

   DHCPv6 provides a mechanism that allows the server to assign or
   delegate both stateful and stateless configuration parameters to
   clients.  The stateful configuration parameters include IPv6
   addresses [<a href="https://tools.ietf.org/html/rfc3315" title="&quot;Dynamic Host Configuration Protocol for IPv6 (DHCPv6)&quot;">RFC3315</a>] and IPv6 prefixes [<a href="https://tools.ietf.org/html/rfc3633" title="&quot;IPv6 Prefix Options for Dynamic Host Configuration Protocol (DHCP) version 6&quot;">RFC3633</a>].  The stateless
   configuration parameters [<a href="https://tools.ietf.org/html/rfc3736" title="&quot;Stateless Dynamic Host Configuration Protocol (DHCP) Service for IPv6&quot;">RFC3736</a>] include, for example, DNS
   [<a href="https://tools.ietf.org/html/rfc3646" title="&quot;DNS Configuration options for Dynamic Host Configuration Protocol for IPv6 (DHCPv6)&quot;">RFC3646</a>], or a Fully Qualified Domain Name (FQDN) of an Address
   Family Transition Router (AFTR) [<a href="https://tools.ietf.org/html/rfc6334" title="&quot;Dynamic Host Configuration Protocol for IPv6 (DHCPv6) Option for Dual-Stack Lite&quot;">RFC6334</a>].  In the scenarios
   described in this document, the DHCPv6 server is deployed in the
   central part of an ISP network.

   RADIUS [<a href="https://tools.ietf.org/html/rfc2865" title="&quot;Remote Authentication Dial In User Service (RADIUS)&quot;">RFC2865</a>] is widely used as the centralized authentication,
   authorization, and user management mechanism for service provision in
   a Broadband access network.  [<a href="https://tools.ietf.org/html/rfc3162" title="&quot;RADIUS and IPv6&quot;">RFC3162</a>], [<a href="https://tools.ietf.org/html/rfc4818" title="&quot;RADIUS Delegated-IPv6-Prefix Attribute&quot;">RFC4818</a>], [<a href="https://tools.ietf.org/html/rfc6519" title="&quot;RADIUS Extensions for Dual- Stack Lite&quot;">RFC6519</a>], and
   [<a href="https://tools.ietf.org/html/rfc6911" title="&quot;RADIUS Attributes for IPv6 Access Networks&quot;">RFC6911</a>] specify the attributes that support the service provision



<span class="grey">Yeh &amp; Boucadair              Standards Track                    [Page 2]</span>
</pre><!--NewPage--><pre class="newpage"><a name="page-3" id="page-3" href="#page-3" class="invisible"> </a>
<span class="grey"><a href="https://tools.ietf.org/html/rfc7037">RFC 7037</a>                  DHCPv6 RADIUS Option              October 2013</span>


   for IPv6-only and IPv6-transition access.  The RADIUS server
   authorizes the Network Access Server (NAS) to assign an IPv6 address
   or prefix from the indicated pool, or to assign an IPv6 address or
   prefix with an explicitly indicated value, and to indicate other
   configuration parameters as per the RADIUS attributes for the
   subscribers.

   When the NAS acts as the distributed DHCPv6 server and RADIUS client
   simultaneously, it communicates with the RADIUS server after
   receiving a request from the DHCPv6 client.  Upon receiving the
   Access-Accept message from the RADIUS server, the NAS then responds
   to the DHCPv6 client's requests per the associated authorization
   information indicated by the RADIUS attributes in the Access-Accept
   message.  When NAS acts as the DHCPv6 relay agent and RADIUS client
   simultaneously, and the centralized DHCPv6 server is co-located with
   the RADIUS server, they may share the same database of users.
   However, when the centralized DHCPv6 server is not located in the
   same place as the RADIUS server, a new communication mechanism is
   needed for the DHCPv6 relay agent to transfer the authorization
   information indicated by the RADIUS attributes to the DHCPv6 server.

<span class="h2"><h2><a class="selflink" name="section-2" href="#section-2">2</a>.  Terminology and Language</h2></span>

   This document specifies a new DHCPv6 option for the DHCPv6 Relay
   Agent to transfer the authorization information of RADIUS attributes
   received in the Access-Accept message from the RADIUS server to the
   centralized DHCPv6 server.  Definitions for terms and acronyms not
   specified in this document are defined in [<a href="https://tools.ietf.org/html/rfc2865" title="&quot;Remote Authentication Dial In User Service (RADIUS)&quot;">RFC2865</a>] and [<a href="https://tools.ietf.org/html/rfc3315" title="&quot;Dynamic Host Configuration Protocol for IPv6 (DHCPv6)&quot;">RFC3315</a>].

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
   "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
   document are to be interpreted as described in [<a href="https://tools.ietf.org/html/rfc2119" title="&quot;Key words for use in RFCs to Indicate Requirement Levels&quot;">RFC2119</a>].

<span class="h2"><h2><a class="selflink" name="section-3" href="#section-3">3</a>.  Network Scenarios</h2></span>

   Figures 1 and 2 show the typical network scenarios where the
   communication mechanism introduced in this document is necessary.  In
   these scenarios, the centralized DHCPv6 server is not co-located with
   the RADIUS server, but both are in the same administrative domain.
   The NAS acts as the DHCPv6 relay agent and the RADIUS client
   simultaneously.  Figure 1 shows the sequence of DHCPv6 and RADIUS
   messages for the IP over Ethernet (IPoE) access model, when the
   access loop adopts the direct Ethernet encapsulation.  Figure 2 shows
   the sequence of DHCPv6 and RADIUS messages for the PPP over Ethernet
   (PPPoE) access model.






<span class="grey">Yeh &amp; Boucadair              Standards Track                    [Page 3]</span>
</pre><!--NewPage--><pre class="newpage"><a name="page-4" id="page-4" href="#page-4" class="invisible"> </a>
<span class="grey"><a href="https://tools.ietf.org/html/rfc7037">RFC 7037</a>                  DHCPv6 RADIUS Option              October 2013</span>


   The mechanism introduced in this document is a generic mechanism and
   might also be employed in other network scenarios where the DHCPv6
   relay agent and the RADIUS client are located in the same device.

   +-------+                   +-------+                    +-------+
   |DHCPv6 |   Access Model:   |  NAS  |                    |RADIUS |
   |Client |       IPoE        |       |                    |Server |
   +-------+                   +-------+                    +-------+
                      RADIUS Client/DHCPv6 Relay Agent

       |                           |                            |
       |---Solicit----------------&gt;|                            |
       |                           |---Access-Request----------&gt;|
       |                           |                            |
       |                           |&lt;--Access-Accept------------|
       |                           |(e.g. Delegated-IPv6-Prefix)|
       |                           |                            |

              DHCPv6 messages             RADIUS messages

                                                            +-------+
                                                            |DHCPv6 |
                                                            |Server |
                                                            +-------+
       |                           |                            |
       |                           |---Relay-forward-----------&gt;|
       |                           |  (OPTION_RADIUS)           |
       |                           |                            |
       |                           |&lt;--Relay-reply -------------|
       |&lt;--Advertise---------------|                            |
       |  (e.g., IA_PD)            |                            |
       |                           |                            |
       |---Request----------------&gt;|                            |
       |  (e.g., IA_PD)            |---Relay-forward-----------&gt;|
       |                           |  (OPTION_RADIUS)           |
       |                           |                            |
       |                           |&lt;--Relay-reply -------------|
       |&lt;--Reply-------------------|                            |
       |  (e.g., IA_PD)            |                            |
       |                           |                            |

              DHCPv6 messages             DHCPv6 messages

   Figure 1: Network Scenario and Message Sequence When Employing DHCPv6
                       RADIUS Option in IPoE Access






<span class="grey">Yeh &amp; Boucadair              Standards Track                    [Page 4]</span>
</pre><!--NewPage--><pre class="newpage"><a name="page-5" id="page-5" href="#page-5" class="invisible"> </a>
<span class="grey"><a href="https://tools.ietf.org/html/rfc7037">RFC 7037</a>                  DHCPv6 RADIUS Option              October 2013</span>


   +-------+                   +-------+                    +-------+
   |DHCPv6 |   Access Model:   |  NAS  |                    |RADIUS |
   |Client |      PPPoE        |       |                    |Server |
   +-------+                   +-------+                    +-------+
                      RADIUS Client/DHCPv6 Relay Agent

       |                           |                            |
       |--PPP LCP Config-Request--&gt;|                            |
       |                           |---Access-Request----------&gt;|
       |                           |                            |
       |                           |&lt;--Access-Accept------------|
       |&lt;----PPP LCP Config-ACK----|(e.g. Delegated-IPv6-Prefix)|
       |                           |                            |

               PPP messages               RADIUS messages

                                                            +-------+
                                                            |DHCPv6 |
                                                            |Server |
                                                            +-------+
       |                           |                            |
       |---Solicit----------------&gt;|                            |
       |                           |---Relay-forward-----------&gt;|
       |                           |  (OPTION_RADIUS)           |
       |                           |                            |
       |                           |&lt;--Relay-reply -------------|
       |&lt;--Advertise---------------|                            |
       |  (e.g., IA_PD)            |                            |
       |                           |                            |
       |---Request----------------&gt;|                            |
       |  (e.g., IA_PD)            |---Relay-forward-----------&gt;|
       |                           |  (OPTION_RADIUS)
       |                           |                            |
       |                           |&lt;--Relay-reply -------------|
       |&lt;--Reply-------------------|                            |
       |  (e.g., IA_PD)            |                            |
       |                           |                            |

              DHCPv6 messages             DHCPv6 messages

   Figure 2: Network Scenario and Message Sequence When Employing DHCPv6
                       RADIUS Option in PPPoE Access

   If the authentication or the authorization through RADIUS fails, the
   associated message sequences will stop.  The NAS acting as the DHCPv6
   relay agent will not forward the message received from the client to
   the DHCPv6 server.  If the authentication or the authorization
   through RADIUS passes, the NAS MUST store the information indicated



<span class="grey">Yeh &amp; Boucadair              Standards Track                    [Page 5]</span>
</pre><!--NewPage--><pre class="newpage"><a name="page-6" id="page-6" href="#page-6" class="invisible"> </a>
<span class="grey"><a href="https://tools.ietf.org/html/rfc7037">RFC 7037</a>                  DHCPv6 RADIUS Option              October 2013</span>


   in the RADIUS attributes received in the Access-Accept message from
   the RADIUS server during the whole session.  How the NAS manages this
   information during the RADIUS session is out of the scope of this
   document.

   After receiving a RENEW (5) message from the DHCPv6 client, the NAS
   SHOULD NOT initiate a new Access-Request/Access-Accept message
   exchange with the RADIUS server.  After receiving a REBIND (6)
   message from the DHCPv6 client, the NAS MUST initiate a new Access-
   Request/Access-Accept message exchange with the RADIUS server, unless
   RADIUS capability is disabled on the NAS.

<span class="h2"><h2><a class="selflink" name="section-4" href="#section-4">4</a>.  DHCPv6 RADIUS Option</h2></span>

   The OPTION_RADIUS is a DHCPv6 option used by the DHCPv6 relay agent
   to carry the authorization information of RADIUS attributes received
   in the Access-Accept message from the RADIUS server.

   The format of the OPTION_RADIUS option is defined as follows:

    0                   1                   2                   3
    0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |         OPTION_RADIUS         |          option-len           |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |            option-data (List of RADIUS Attributes)
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

   option-code      81
   option-len       Length of the option-data in octets
   option-data      List of one or more RADIUS attributes


   The option-data of OPTION_RADIUS is a list of one or more RADIUS
   attributes received in the Access-Accept message from the RADIUS
   server.  The format of RADIUS attributes is defined in <a href="https://tools.ietf.org/html/rfc2865#section-5">Section&nbsp;5 of
   [RFC2865]</a> as well as Sections <a href="#section-2.1">2.1</a> and <a href="#section-2.2">2.2</a> of [<a href="https://tools.ietf.org/html/rfc6929" title="&quot;Remote Authentication Dial In User Service (RADIUS) Protocol Extensions&quot;">RFC6929</a>].  If multiple
   attributes with the same type (including the Long Extended Type
   defined in <a href="https://tools.ietf.org/html/rfc6929#section-2.2">Section&nbsp;2.2 of [RFC6929]</a>) are present, the order of
   attributes with the same type MUST be the same as that received from
   the RADIUS server.  The OPTION_RADIUS can only contain the RADIUS
   attributes listed in the "RADIUS Attributes Permitted in DHCPv6
   RADIUS Option" registry.








<span class="grey">Yeh &amp; Boucadair              Standards Track                    [Page 6]</span>
</pre><!--NewPage--><pre class="newpage"><a name="page-7" id="page-7" href="#page-7" class="invisible"> </a>
<span class="grey"><a href="https://tools.ietf.org/html/rfc7037">RFC 7037</a>                  DHCPv6 RADIUS Option              October 2013</span>


   According to the network scenarios described in <a href="#section-3">Section 3</a>, the
   OPTION_RADIUS should appear in the RELAY-FORW (12) message relaying
   SOLICIT (1), REQUEST (3), and REBIND (6) from the DHCPv6 client and
   may appear in the RELAY-FORW (12) relaying any other message from the
   DHCPv6 client.

<span class="h3"><h3><a class="selflink" name="section-4.1" href="#section-4.1">4.1</a>.  RADIUS Attributes Permitted in DHCPv6 RADIUS Option</h3></span>

   The RADIUS attributes listed in the following table are the initial
   attributes registered in the "RADIUS Attributes Permitted in DHCPv6
   RADIUS Option" registry.  New RADIUS attributes can be added to this
   list after Expert Review [<a href="https://tools.ietf.org/html/rfc5226" title="&quot;Guidelines for Writing an IANA Considerations Section in RFCs&quot;">RFC5226</a>].

   Type Code  Attribute                   Reference
   26         Vendor-Specific             [<a href="https://tools.ietf.org/html/rfc2865" title="&quot;Remote Authentication Dial In User Service (RADIUS)&quot;">RFC2865</a>]
   123        Delegated-IPv6-Prefix       [<a href="https://tools.ietf.org/html/rfc4818" title="&quot;RADIUS Delegated-IPv6-Prefix Attribute&quot;">RFC4818</a>]
   144        DS-Lite-Tunnel-Name         [<a href="https://tools.ietf.org/html/rfc6519" title="&quot;RADIUS Extensions for Dual- Stack Lite&quot;">RFC6519</a>]
   168        Framed-IPv6-Address         [<a href="https://tools.ietf.org/html/rfc6911" title="&quot;RADIUS Attributes for IPv6 Access Networks&quot;">RFC6911</a>]
   169        DNS-Server-IPv6-Address     [<a href="https://tools.ietf.org/html/rfc6911" title="&quot;RADIUS Attributes for IPv6 Access Networks&quot;">RFC6911</a>]
   171        Delegated-IPv6-Prefix-Pool  [<a href="https://tools.ietf.org/html/rfc6911" title="&quot;RADIUS Attributes for IPv6 Access Networks&quot;">RFC6911</a>]
   172        Stateful-IPv6-Address-Pool  [<a href="https://tools.ietf.org/html/rfc6911" title="&quot;RADIUS Attributes for IPv6 Access Networks&quot;">RFC6911</a>]


   Note: The RADIUS attribute's 'Length' defined in <a href="https://tools.ietf.org/html/rfc2865#section-5">Section&nbsp;5 of
   [RFC2865]</a> includes the length of 'Type' and 'Length' fields.

<span class="h2"><h2><a class="selflink" name="section-5" href="#section-5">5</a>.  DHCPv6 Relay Agent Behavior</h2></span>

   If the Relay Agent is configured to send OPTION_RADIUS, and the
   Access-Accept message from the RADIUS server contained RADIUS
   attributes permitted for use in OPTION_RADIUS, the Relay Agent MUST
   include OPTION_RADIUS in the RELAY-FORW (12) message.  The DHCPv6
   relay agent adds the permitted RADIUS attributes into OPTION_RADIUS
   one by one; if multiple attributes with the same type are present,
   the order of attributes with the same type MUST be the same as that
   received from the RADIUS server.

<span class="h2"><h2><a class="selflink" name="section-6" href="#section-6">6</a>.  DHCPv6 Server Behavior</h2></span>

   Upon receipt of the RELAY-FORW (12) message with OPTION_RADIUS from a
   relay agent, the DHCPv6 server that supports OPTION_RADIUS SHOULD
   extract and interpret the RADIUS attributes in the OPTION_RADIUS and
   use that information to select configuration parameters for the
   requesting client.  If the DHCPv6 server does not support
   OPTION_RADIUS, the DHCPv6 server MUST silently discard this option.






<span class="grey">Yeh &amp; Boucadair              Standards Track                    [Page 7]</span>
</pre><!--NewPage--><pre class="newpage"><a name="page-8" id="page-8" href="#page-8" class="invisible"> </a>
<span class="grey"><a href="https://tools.ietf.org/html/rfc7037">RFC 7037</a>                  DHCPv6 RADIUS Option              October 2013</span>


<span class="h2"><h2><a class="selflink" name="section-7" href="#section-7">7</a>.  DHCPv6 Client Behavior</h2></span>

   OPTION_RADIUS is only exchanged between the relay agents and the
   servers.  DHCPv6 clients are not aware of the usage of OPTION_RADIUS.
   DHCPv6 clients MUST NOT send OPTION_RADIUS and MUST ignore
   OPTION_RADIUS if received.

<span class="h2"><h2><a class="selflink" name="section-8" href="#section-8">8</a>.  Security Considerations</h2></span>

   Known security vulnerabilities of the DHCPv6 and RADIUS protocols may
   apply to their options.  Security issues related with DHCPv6 are
   described in <a href="https://tools.ietf.org/html/rfc3315#section-23">Section&nbsp;23 of [RFC3315]</a>.  Security issues related with
   RADIUS are described in <a href="https://tools.ietf.org/html/rfc2865#section-8">Section&nbsp;8 of [RFC2865]</a>, <a href="https://tools.ietf.org/html/rfc3162#section-5">Section&nbsp;5 of
   [RFC3162]</a>, and <a href="https://tools.ietf.org/html/rfc6929#section-11">Section&nbsp;11 of [RFC6929]</a>.

   The mechanism described in this document may introduce a new attack
   vector against the DHCPv6 server in cases where the DHCPv6 relay
   agent is compromised.  By forging the RADIUS attributes contained in
   the OPTION_RADIUS of the RELAY-FORW (12) messages, the attacker may
   influence the parameter assignment on the DHCPv6 server for the
   DHCPv6 clients.  However, as described in the <a href="#section-3">Section 3</a>, NAS always
   belongs to the same administrative domain of the DHCPv6 server in the
   real deployment.

   Network administrators should be aware that although RADIUS messages
   are encrypted, DHCPv6 messages are always unencrypted.  It is
   possible that some RADIUS vendor-specific attributes might contain
   sensitive or confidential information.  Network administrators are
   strongly advised to prevent such information from being included in
   DHCPv6 messages.

   If the use of vendor-specific attributes with confidential content is
   required, administrators are advised to use IPsec with encryption to
   protect the confidentiality of the RADIUS attributes.  Relay agents
   and servers implementing this specification MUST support the use of
   IPsec Encapsulating Security Payload (ESP) with encryption in
   transport mode, according to <a href="https://tools.ietf.org/html/rfc4303#section-3.1.1">Section&nbsp;3.1.1 of [RFC4303]</a> and
   <a href="https://tools.ietf.org/html/rfc3315#section-21.1">Section&nbsp;21.1 of [RFC3315]</a>.

<span class="h2"><h2><a class="selflink" name="section-9" href="#section-9">9</a>.  IANA Considerations</h2></span>

   IANA has assigned OPTION_RADIUS (81) in the "DHCP Option Codes"
   registry, as defined in <a href="#section-4">Section 4</a>.  In addition, IANA has created a
   new registry entitled "RADIUS Attributes Permitted in DHCPv6 RADIUS
   Option" in the "Dynamic Host Configuration Protocol for IPv6
   (DHCPv6)" registry, as defined in <a href="#section-4.1">Section 4.1</a>.  The new registry
   enumerates the RADIUS Attributes Types
   (<a href="http://www.iana.org/assignments/radius-types">http://www.iana.org/assignments/radius-types</a>) that are permitted for



<span class="grey">Yeh &amp; Boucadair              Standards Track                    [Page 8]</span>
</pre><!--NewPage--><pre class="newpage"><a name="page-9" id="page-9" href="#page-9" class="invisible"> </a>
<span class="grey"><a href="https://tools.ietf.org/html/rfc7037">RFC 7037</a>                  DHCPv6 RADIUS Option              October 2013</span>


   inclusion in the DHCPv6 RADIUS option.  The allocation policy of this
   "RADIUS Attributes Permitted in DHCPv6 RADIUS Option" registry is
   Expert Review per [<a href="https://tools.ietf.org/html/rfc5226" title="&quot;Guidelines for Writing an IANA Considerations Section in RFCs&quot;">RFC5226</a>].  Designated experts should carefully
   consider the security implications of allowing the relay agent to
   include new RADIUS attributes to this registry.

<span class="h2"><h2><a class="selflink" name="section-10" href="#section-10">10</a>.  Acknowledgements</h2></span>

   Thanks to Tomek Mrugalski, Bernie Volz, Gaurav Halwasia, and Roberta
   Maglione for their thorough review comments in the DHC working group
   mailing list.  Thanks also to Ted Lemon for his continuous
   encouragement and technical guidance.

<span class="h2"><h2><a class="selflink" name="section-11" href="#section-11">11</a>.  References</h2></span>

<span class="h3"><h3><a class="selflink" name="section-11.1" href="#section-11.1">11.1</a>.  Normative References</h3></span>

   [<a name="ref-RFC2119" id="ref-RFC2119">RFC2119</a>]  Bradner, S., "Key words for use in RFCs to Indicate
              Requirement Levels", <a href="https://tools.ietf.org/html/bcp14">BCP 14</a>, <a href="https://tools.ietf.org/html/rfc2119">RFC 2119</a>, March 1997.

   [<a name="ref-RFC2865" id="ref-RFC2865">RFC2865</a>]  Rigney, C., Willens, S., Rubens, A., and W. Simpson,
              "Remote Authentication Dial In User Service (RADIUS)", <a href="https://tools.ietf.org/html/rfc2865">RFC</a>
              <a href="https://tools.ietf.org/html/rfc2865">2865</a>, June 2000.

   [<a name="ref-RFC3315" id="ref-RFC3315">RFC3315</a>]  Droms, R., Bound, J., Volz, B., Lemon, T., Perkins, C.,
              and M. Carney, "Dynamic Host Configuration Protocol for
              IPv6 (DHCPv6)", <a href="https://tools.ietf.org/html/rfc3315">RFC 3315</a>, July 2003.

   [<a name="ref-RFC4303" id="ref-RFC4303">RFC4303</a>]  Kent, S., "IP Encapsulating Security Payload (ESP)", <a href="https://tools.ietf.org/html/rfc4303">RFC</a>
              <a href="https://tools.ietf.org/html/rfc4303">4303</a>, December 2005.

   [<a name="ref-RFC4818" id="ref-RFC4818">RFC4818</a>]  Salowey, J. and R. Droms, "RADIUS Delegated-IPv6-Prefix
              Attribute", <a href="https://tools.ietf.org/html/rfc4818">RFC 4818</a>, April 2007.

   [<a name="ref-RFC5226" id="ref-RFC5226">RFC5226</a>]  Narten, T. and H. Alvestrand, "Guidelines for Writing an
              IANA Considerations Section in RFCs", <a href="https://tools.ietf.org/html/bcp26">BCP 26</a>, <a href="https://tools.ietf.org/html/rfc5226">RFC 5226</a>,
              May 2008.

   [<a name="ref-RFC6519" id="ref-RFC6519">RFC6519</a>]  Maglione, R. and A. Durand, "RADIUS Extensions for Dual-
              Stack Lite", <a href="https://tools.ietf.org/html/rfc6519">RFC 6519</a>, February 2012.

   [<a name="ref-RFC6911" id="ref-RFC6911">RFC6911</a>]  Dec, W., Sarikaya, B., Zorn, G., Miles, D., and B.
              Lourdelet, "RADIUS Attributes for IPv6 Access Networks",
              <a href="https://tools.ietf.org/html/rfc6911">RFC 6911</a>, April 2013.

   [<a name="ref-RFC6929" id="ref-RFC6929">RFC6929</a>]  DeKok, A. and A. Lior, "Remote Authentication Dial In User
              Service (RADIUS) Protocol Extensions", <a href="https://tools.ietf.org/html/rfc6929">RFC 6929</a>, April
              2013.



<span class="grey">Yeh &amp; Boucadair              Standards Track                    [Page 9]</span>
</pre><!--NewPage--><pre class="newpage"><a name="page-10" id="page-10" href="#page-10" class="invisible"> </a>
<span class="grey"><a href="https://tools.ietf.org/html/rfc7037">RFC 7037</a>                  DHCPv6 RADIUS Option              October 2013</span>


<span class="h3"><h3><a class="selflink" name="section-11.2" href="#section-11.2">11.2</a>.  Informative References</h3></span>

   [<a name="ref-RFC3162" id="ref-RFC3162">RFC3162</a>]  Aboba, B., Zorn, G., and D. Mitton, "RADIUS and IPv6", <a href="https://tools.ietf.org/html/rfc3162">RFC</a>
              <a href="https://tools.ietf.org/html/rfc3162">3162</a>, August 2001.

   [<a name="ref-RFC3633" id="ref-RFC3633">RFC3633</a>]  Troan, O. and R. Droms, "IPv6 Prefix Options for Dynamic
              Host Configuration Protocol (DHCP) version 6", <a href="https://tools.ietf.org/html/rfc3633">RFC 3633</a>,
              December 2003.

   [<a name="ref-RFC3646" id="ref-RFC3646">RFC3646</a>]  Droms, R., "DNS Configuration options for Dynamic Host
              Configuration Protocol for IPv6 (DHCPv6)", <a href="https://tools.ietf.org/html/rfc3646">RFC 3646</a>,
              December 2003.

   [<a name="ref-RFC3736" id="ref-RFC3736">RFC3736</a>]  Droms, R., "Stateless Dynamic Host Configuration Protocol
              (DHCP) Service for IPv6", <a href="https://tools.ietf.org/html/rfc3736">RFC 3736</a>, April 2004.

   [<a name="ref-RFC6334" id="ref-RFC6334">RFC6334</a>]  Hankins, D. and T. Mrugalski, "Dynamic Host Configuration
              Protocol for IPv6 (DHCPv6) Option for Dual-Stack Lite",
              <a href="https://tools.ietf.org/html/rfc6334">RFC 6334</a>, August 2011.

Authors' Addresses

   Leaf Y. Yeh
   Freelancer Technologies
   P. R. China

   EMail: leaf.yeh.sdo@gmail.com


   Mohamed Boucadair
   France Telecom
   France

   EMail: mohamed.boucadair@orange.com

















Yeh &amp; Boucadair              Standards Track                   [Page 10]

</pre><br>
<span class="noprint"><small><small>Html markup produced by rfcmarkup 1.108, available from
<a href="http://tools.ietf.org/tools/rfcmarkup/">http://tools.ietf.org/tools/rfcmarkup/</a>
</small></small></span>

</body></html>